Bump org.eclipse.platform:org.eclipse.core.runtime from 3.31.0 to 3.31.100 #3949
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [org.eclipse.platform:org.eclipse.core.runtime](https://github.com/eclipse-platform/eclipse.platform) from 3.31.0 to 3.31.100. - [Commits](https://github.com/eclipse-platform/eclipse.platform/commits) --- updated-dependencies: - dependency-name: org.eclipse.platform:org.eclipse.core.runtime dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Test Results 597 files 597 suites 4h 17m 35s ⏱️ Results for commit 6642538. ♻️ This comment has been updated with latest results. |
akurtakov
force-pushed
the
dependabot/maven/org.eclipse.platform-org.eclipse.core.runtime-3.31.100
branch
from
f987603 to
88cdced
Compare
2024-06 Due to split package this update has to go together with core.runtime.
akurtakov
force-pushed
the
dependabot/maven/org.eclipse.platform-org.eclipse.core.runtime-3.31.100
branch
3 times, most recently
from
6c275f5 to
da77109
Compare
And adjust tests for that.
akurtakov
force-pushed
the
dependabot/maven/org.eclipse.platform-org.eclipse.core.runtime-3.31.100
branch
from
da77109 to
c349b08
Compare
So no old org.eclipse.core.runtime package content with different signature ends up transitively.
|
/request-license-review |
License review requests: After all reviews have concluded, re-run the license-vetting check from the Github Actions web-interface to update its status. Workflow run (with attached summary files): |
|
Merging despite the xz-java issue as it's smth Platform ships for years already so looks like a glitch in tool. |
dependabot
bot
deleted the
dependabot/maven/org.eclipse.platform-org.eclipse.core.runtime-3.31.100
branch
laeubi
added
the
backport-to-tycho-4.0.x
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
3 similar comments
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Bumps org.eclipse.platform:org.eclipse.core.runtime from 3.31.0 to 3.31.100.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)